Mapping of system errors

[jasper]

COM errors map to CAPE-OPEN errors on the COBIA side. Similarly COBIA errors map to ECapeUser errors on the COM side.

Perhaps COM system errors, such as E_POINTER, E_FAIL, should map to COBIA system errors such as COBIAERR_CriticalError and COBIAERR_NullPointer.

In addition to this making sense, it also allows the CAPE-OPEN Test Suite to test that CAPE_OPEN errors are raised instead of system errors, where expected.

[jasper]

The following errors are mapped between COBIA and COM as system errors:

		addMapping(COBIAERR_NoError,NOERROR);
		addMapping(COBIAERR_UnknownError,E_FAIL);
		addMapping(COBIAERR_InvalidArgument,E_INVALIDARG);
		addMapping(COBIAERR_NoSuchInterface,E_NOINTERFACE);
		addMapping(COBIAERR_Denied,E_ACCESSDENIED);
		addMapping(COBIAERR_NotImplemented,E_NOTIMPL);
		addMapping(COBIAERR_OutOfMemory,E_OUTOFMEMORY);
		addMapping(COBIAERR_CriticalError,E_UNEXPECTED);
		addMapping(COBIAERR_NullPointer,E_POINTER);

All remaining errors are mapped as CAPE-OPEN errors with the error string obtained from the system.

[jasper]

In [4041998650e72fda3f9cc269d099a80820b845a0]:

fix #173, fix #175, fix #176

[jasper]

In [441662c9e3aa4235f88658ca04195bdc2620178e]:

fix #173, fix #176, fix #175