Please don't use names following the MFC naming convention [ie. C followed by class name] because of the infinte potential name conflicts, inlcuding FUTURE classes library vendors(Microsoft in this case) will add. Notice that Borland uses T followed by class name, and other vendors have OTHER prefixes, so as to minimize the inconvieniences of mixing libraries.

Also, make sure and put ALL of your library into a namespace, so even if conflicts arise, the user has access to ALL classes to both libraries (even though it will be less convienient than no conflicts).

I myself am programming a more basic library: various tree containers in STL style, and have chosen to use a unique prefix AND a namespace, and then ANOTHER namespace that uses more common names. This lets the user include the first namespace in ANY case, but if he/she knows there is no conflict, they can include the second namespace (or just parts of it) to access the elements without needing the prefixes. Example:
namespace Vx // my company prefix
{
class VxTree;
class VxBTree;
class VxBinarySearchTree;
};
namespace VxPlain
{
typedef Vx::VxTree tree;
typedef Vx::VxBTree btree;
};

Anyway, good luck sir.