container issues
----------------

There's at least one good "gotcha" when working with the OMF
containers. While they share a common add/remove interface
using Object pointers, we often pass primitives and the
containers themselves as regular stack-based data structures.
This can become a problem when discussing lists of stack-
based objects, because we use their pointers to store them.

In general, care should be taken when using containers
with primitive types - which is unfortunate.

One solution might be to create a "boxing" object that
is a) dynamically allocated to contain stack-based objects
and b) is automatically garbage collected when the list
is cleared. Any solution to this should be completely
hidden to the user. This would entails some specific
code in the container classes to recognize the addition
of primitive types and to "box" them on addition.