Switches vsArray::RemoveItem to be less smart.

Order can matter in a vector -- don't reorder elements inside
vsArray::RemoveItem!

Yes, that approach is faster.  But client code can do it manually if
that's actually what they want.  If what I really want is a set (in
which order doesn't matter), I should provide one, or just use std::set.