End Google Ads 201810 - BS.net 01 --> With the help of "Superman", I was able to prevent all but one memory leak generated by the 'new' operator:

{164} client block at 0x00187CA0, subtype c0, 28 bytes long. a CObject object at $00187CA0, 28 bytes long

Questions: 1. I understand most of what the Visual Studio 2008 teaches. Am I doing something incorrectly
to generate this leak?
2. Do I have to do something with this, or will the memory be released upon exiting Visual Studio.

There are several 'normal block' memory leaks also indicated. They take the form of:

f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {166} normal block at 0x00187D68, 28 bytes long.
Data: 2C FB 16 65 05 00 00 00 05 00 00 00 01 00 00 00

Questions: 1. This appears to be generated inside an executable supplied by Visual Studio. Is this a Microsoft "bug"?
If so, what am I doing to cause this and others of similar form?
2. Same question as #2 above.
3. FWIW, my System Disk Management dialog shows "f:\" as one of my DVD reader/writers. Does Visual Studion
"count noses" differently than Vista 64 does?

Thanks again,

Barry