Cook Computing: Deterministic Finalization

Tech Blog: "smart pointers are of no use because destructors are called non-deterministically for managed types and so there is no way of knowing when a reference to a managed type has gone out of scope.
The lack of DF, while adding extra work around resource management, does not bother me unduly. My experience with large-scale C++ projects is that memory corruption is a much bigger long-term problem and we can avoid that completely if we stick to verifiable managed code (bye bye C++, though I remember reading that a future version of Managed C++ will be able to generate managed code, presumably allowing only a small subset of C++). Failure to release resources is detected fairly early on during system testing whereas memory corruption can lurk for a very long time before showing itself, usually at an important customer site."