Fuse tight composer

We can have situations where during the course of analysis a given object at a given edge may slowly grow until it becomes full. How should we deal with intersection objects that contain such objects? How should we deal with maps and other data structures that contain them?

One option is to check for fullness once and never change.

Another option is to keep checking objects for fullness. If we choose this route then this is the code location where we should check if memLocsMap[key]->isFullML()/s_it->second->isFullML() and delete it.