I've not had any time to track this down properly but if you have a sprite that has yet to have its position set via a SetSpritePosition command then it returns a false positive when you check for collisions with it under certain circumstances. It seems to use the coordinates of another (next or previous ID?) sprite when calculating sprite collisions. I'll track down the exact circumstances at some stage but thought I'd mention it as it had me fooled for a couple of hours (didn't help that I requested feedback on various variables incorrectly so was reading incorrect data whilst hunting for the bug! LOL)!
If a sprite hasn't been positioned yet, I feel it should never give a positive for collisions.
Using Tier 1 AppGameKit V2
Started coding with AMOS (Thanks Francois Lionet)