1. I assume this is implemented in such a way that Biltz knows which list an object is in without actually searching the list. So checking =Null should not slow down as the number of deleted objects increases.
2. It is true that memory used by Type objects goes up but never down. It is always a kind of 'high water mark'. I suppose you could cook up an example of this which causes problems. But in practice I doubt you will see any bad effects.
2. It is true that memory used by Type objects goes up but never down. It is always a kind of 'high water mark'. I suppose you could cook up an example of this which causes problems. But in practice I doubt you will see any bad effects.