Special considerations when using the "new" operator?

I have been trying, now, for the past week or so to build up edgelists for stencil shadowing. Many times I've redesigned them: first as a list manager, second on TSShape, and finally on TSMesh. My class is relatively simple (this is from memory, so any syntax errors -- please be lenient):

struct SVShadowEdge
{
   U32 vertices[2];
   U32 triangles[2];
};

class SVEdgeList
{
   public:
      Vector<SVShadowEdge> mList;
      TSMesh* mesh;
      bool listActive;

   public:
      SVEdgeList();
      ~SVEdgeList();

      void RebuildEdgeList(TSMesh* meshObj);
};

Within TSMesh, I have created a simple pointer to a SVEdgeList called edgeList:

class TSMesh
{
   ...

   SVEdgeList* edgeList
};

This holds a ref to a new object that will be created in TSMesh::assembleMesh(). There is a call in that method to the following function. I added a method to TSMesh to call the edgelist builder (this is from memory too, so forgive me for syntax):

void TSMesh::buildMeshEdges()
{
   if (!edgeList)
   {
      // There is a determination of whether this is
      // a good mesh (Standard or Skin) but I cannot
      // remember the exact code...  It goes into
      // "badMesh"

      if ((indicies.size() > 0) && !badMesh)
      {
         edgeList = new SVEdgeList();
         edgeList->RebuildEdgeList(this);
      } else {
         edgeList = NULL;
      }
   }
}

The problem I'm having is that it works fine for about 3 to 4 meshes. On the fifth call, when it hits the call to new I get an access violation. The violation occurs in PlatformMemory.cc in the treeRemove method once it has determined that there is a header. It then tries to assign the nextQueue and prevQueue, but what I see is that prev and next refer to 0x00000007 and 0x00000013. It's the same each time and it's blowing up at this point.

I've tried disabling the TGE memory manager, turned on DEBUG_GUARD, and examined numerous other classes that do something similar. For instance, ShapeBase has a pointer to the Shadow class, which it creates on the fly with a call to "mShadow = new Shadow()". It doesn't seem that I'm doing anything odd here.

Any ideas?

- Brett