How to reproduce:
1. Create a new project
2. Import the Profile Analyzer package
3. Select the Compare tab
4. Load the data (capture.pdata to the first slot and capture2.pdata to the second slot)
5. Expand the Marker Columns dropdown list and select Count Totals
6. Expand the Units dropdown list and select Microseconds
7. Hover on any of the '< Count' or '> Count' values in the Marker Comparison table

Expected result: the value is displayed as a difference between two integers (Count Right and Count Left)
Actual result: the value is displayed as a difference but converted to time and multiplied by a 1000

Reproducible with: 2018.4.20f1 (0.5.0 - preview.1, 0.6.0 - preview.1) 2019.3.6f1 (0.5.0 - preview.1, 0.6.0 - preview.1),
2020.1.0b2 (0.5.0 - preview.1, 0.6.0 - preview.1) , 2020.2.0a5 (0.5.0 - preview.1, 0.6.0 - preview.1)
Could not test with: 2017.4.38f1 (package unavailable)
Could not test with package version: 0.4.0 (Marker Columns not introduced)

Notes:
1. See the attached video or images on how to reproduce the issue
2. Count difference values are considered to be time values (displayed as 'ms' or 'us'), therefore they get converted to microseconds leading to a wrong result
3. The same issue occurs with '< Frame Count' and '> Frame Count' values in the 'Count per Frame' display