Data Managment
==============
1. Every DSData obtained from (DSBinaryFormat, DSRepresentation, DSDataManager)
should be returned. It is not (in any case) capable of self-destruction.


Further API Development Notes
=============================
1. The realisations of 'dsFormat' and 'dsRepresentation' are returning pointers
on static structures  (dsBinaryFormatNative, dsBinaryFormatOPCXML, ...). And
there are no 'Return' call.
I think in the most cases it is most appropriate behavior and extension of the
base interface with destructor function looks to me a bad idea. However, in 
some circustmances it could be necessary to provide dynamic structure (for 
example to control instances allocation/free calls). In that case the 
realisation classes should be extended with Create/Destroy functions 
dsBinaryFormatCreateNative/dsBinaryFormatDestroyNative. And the developer 
would deciede if he need simple version or version with extended functionality.

2. At the moment the DataHandlers intended for the data conversion are using
associated FormatInstances (DSDataManagerFast, DSRepresentationBinary).
It works, since Pipe,Copy,Destroy methods at the moment are not using any 
internal DSFormatInstance data structures for the proccesing. However, if this
behavior would be changed, the all this handlers should be forced to allocate
standalone FormatInstances.