How to reproduce:
1. Download the user-attached profiling data(capture.pdata)
2. Create a new Unity project
3. Import the Profile Analyzer package and load the data
4. In Filters set threads to 'All'
5. Sort the markers by Median
6. Right-click the 'Semaphore.WaitForSignal' entry and select 'Select Frames that contain this marker (within whole data set)'
7. See the graph at the top of the window and the Frame Summary at the top-right

Expected result: frame range is highlighted correctly for the graph, Frame Count matches the Frame Range
Actual result: frame range is not highlighted correctly for the graph, Frame Count does not match the Frame Range(299 frames in range 57-289)

Reproducible with: 2018.4.19f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Could not test with: 2017.4.38f1(package unavailable)

Reproducible with package versions: preview.5 - 0.4.0, preview.1 - 0.6.0

Notes:
Also reproducible from scratch; for example, profiling the Editor and viewing this information for PanelUpdate.ProfilerWindow I was seeing a Frame Count of 5, but a Frame Range of 1895-1630