Answers the question of how much memory the various standard containers use to store the same number of objects of the same type T.

Memory management is scary. It should be: A lot can go wrong--often very wrong. But a moderately experienced C or C++ programmer can learn and understand memory hazards completely.

Matthew and Bjorn update the well-known Rule of The Big Three, explaining which one of those member functions is not always needed.

Explains why a class that provides its own class-specific operator new(), or operator new[](), should also provide corresponding class-specific versions of plain new, in-place new, and nothrow new.

This article follows through the implementation of a smart pointer class that overcames deficiencies of existing smart pointer implementations.

Delves deeper into the question of what operator new() failures mean, and how best to detect and handle them.

Presents a list of simple, powerful techniques that can be used to deal with memory in C++ programs.

Stephen Dewhurst discusses how the various features of C++ are used together in memory management, how they sometimes interact in surprising ways, and how to simplify their interactions.

Show how garbage collection works and what it actually costs.

Using several features of the language, this article presents a framework for resource allocation which is temporally deterministic, provides for callback, provides memory pools, and can provide for deadlock prevention.