Quote Originally Posted by 25205899 View Post
what is the scenario in which an object would call my "new" but would be deleted elsewhere despite the fact that the delete is overloaded just as the "new" was.
We don't know if these are facts until we see the code/project. Many times we get posters swearing that they did this or that, and when we see the code, it isn't the case.

Why not build release versions of everything and retest? If you no longer get the error, then that should be a clue. Mixing up runtime libraries between release/debug/boost, especially when it comes to global/overloaded new and delete, would be a cause for concern.

Regards,

Paul McKenzie