Hi!
First you should have a look at some old posts about this in the archive.
Visual studio will print out a message about memory leaks for any object that is not deleted before the application terminates, this does NOT mean that it is a memory leak.
One example is that you allocate a single object at the start and use this through out the lifetime of the application and igonore to delete it at termination, this is not a memory leak but will be displayed as such by VS.
OCC use it's own memory allocator and I guess this allocates lots of big chunks that is then used to allocate smaller objects and it is possible that it is those you see.
But then, of course it is also possible that you do have a memory leak...,
in the end, to get any use of the leak detector in VS you must have applications and libraries that free all objects at the end vene if it not needed, otherwise you ruin the idea with the leak detector.
Commenter-1