14 Apr
2008
14 Apr
'08
1:18 p.m.
The debugging versions of Microsoft's libraries have leaks built in at no extra charge. If the leak does not go away in a "release" build, then worry about it.
An extremely simple piece test, containing just one stack-created object, is causing boost.test to report a memory leak.