Fixing problems

[Paul <ele...@ya...>]

Hi,

Why do you need to follow an erase() with an optimise() call?  Is it 
possible to keep the tree correct when erasing?  Is this a bug or by design?

Is optimise() always required, even after an insert() ?

This is a huge problem if you want to remove a bunch of items...

Cheers
Paul