Static or dynamic linking the CRT, MFC, ATL, etc

Question

Back in the 90s when I first started out with MFC I used to dynamically link my apps and shipped the relevant MFC DLLs. This caused me a few issues (DLL hell!) and I switch

Answer 1

Most definitely.

Allocation is done on a 'static' heap. Since allocation an deallocation should be done on the same heap, this means that if you ship a library, you should take care that client code can not call 'your' p = new LibClass() and delete that object itself using delete p;.

My conclusion: either shield allocation and deallocation from client code, or dynamically link the CRT.