Update for SpawnManagerClass changes in YRpp.
Fix for the remove parameter to AnnounceInvalidPointer

It is a real bool, not a BOOL; the last three bytes contain garbage. Checking garbage against FALSE will wrongfully almost always yield true.
Check alliances on open-topped Abductors.

Without this, abducted units will fire out of the transport even if they never changed ownership. And they'd still fight for their own side, without a chance of being killed.
Const for ChronoWarpContainer equality operator.
Update for YRpp change: FindItemIndex and reference parameter.
Resize the Verses vectors only once.
VectorClass::start() renamed to begin().
YRpp update: F2I() now returns an int
Break only breaks out of the inner loop. Use return instead.
Update for the YRpp BombClass changes.
Included <algorithm> for std::min and std::max.

This is required to make the code compile with VC++ 2013.
Related to #1248448: Alpha image exists after object destroyed

If an object was destroyed, its alpha image was only deallocated if the object currently had a LineTrailer. The hook has been moved before the LineTrailer check.
Alloc/Dealloc difference for alpha lights (no bug)

Alpha lights are allocated on the game's heap by GAME_ALLOC, but Ares uses 'delete' to destroy them. 'delete' calls the virtual destructor (with the argument 1); this means the game's 'operator delete' is called after the destructor ran. All well in this case (allocating one the dll's heap would be a bug).

GAME_DEALLOC also calls the virtual destructor (but with argument 0). This skips the call to the game's 'operator delete'. GAME_DEALLOC then goes on and calls the game's 'operator delete' explicitly. No difference, but the name of GAME_DEALLOC makes it clear the alpha light has been allocated on the game's heap.

(Also added some comments that the iterators have been invalidated by destroying an alpha light.)