There are several issues dealing with the fact that flight recordings can contain events that are partially temporally outside the current recording, which causes charts to be rendered with a much larger time range than the actual recording. Several ways to resolve this have been proposed, but they all suffer from not knowing what the exact times are that each chunk used to create an IItemCollection represent. This is information that is contained in the recording and is parsed and read into the chunk metadata, so I propose that we simply expose this data in the IItemCollection interface.