step 1: fix log simulator crash that happens when you jump from last frame to first and vice versa.
		- somehow lastFrameInfo doesn't get updated fast enough resulting in current frameTime and 
		last frameTime being the same, which results in false for 
		ASSERT(getFrameInfo().getTimeInSeconds() - lastFrameInfo.getTimeInSeconds() > 0) 
		(line 86 in MultiKalmanBallLocator.cpp)
	
step 2:
open the game log in logsimulator
frame 886: bug with association of percept/model
steps to recreate: open frame and hit r until maximum amount of possible models get created for the two percepts
                   this is observable easily when step 1 is done and the fieldviewer receives the MultiKalmanBallLocator 
				   percepts - activate debug requests PerceptionsVisualizer -> CamBottom and CamTop 
				   and PerceptionsVisualizer -> field -> ball_percept

step 3:
When the ball moves from bottom camera to top camera a new ball model gets created. The ball percept
is correct and thus gets associated with the new ball model. The old ball model persists too long and
doesn't move at this point anymore. This results in the robot after kicking (and the ball moving away from
the robot) kicking again at the position the ball used to be before the initial kick.

This behavior is observable in the game log between frame 870 and 1100.