Fix for event number when using more than one input file at the same time

The event number was changed by each input source resulting in wrong behaviour.
Now the input sources keep track of the event number themselves.  Ideally the
event number would be kept track of one level above, but then m_firstEvent is
not known. Likewise the output module is not aware of the number of skipped
events.