remove the need for an atomic in TrackBestTrackCreator

remove the need for an atomic in TrackBestTrackCreator by explicitly returning the relevant information... on top of that, this will actually make sure that the counter will be reproducible in multi-threaded running, as even though it was atomic, there was only one counter that multiple threads would be incrementing and resetting, giving results that depend on the ordering of the threads, whereas now each thread has its own counter.