Freeing memory allocated in a different dll?

As sean has already said, the release build simply ignores that delete statement, so the best you can hope for is a memory leak.

Most likely, the release build has the same problem, but release builds don't assert. They just ignore the problem. You might never see an issue.

Or you might see data corruption. Or you might see a crash. Maybe only your users will experience bugs that you are simply not able to reproduce.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.