I have a freeware RAM monitor running (on Vista), which is called RamBooster.  It registers about 4MB of loss with each run of the script, which is doesn't do for the cloth.  It's exactly the same RAM loss I experienced with the earlier version of the multi-actor shrinkwrap.  Presumably I just need to track down where I'm looping references.  Do you pass any references in the hit data?  If it isn't all fresh copies, that might be the source of my problem, since I del the Mesh instance which created the hit list, but keep the hit list for the subsequent distance screening loop.

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.