Wrong span duration using 0.8.0-beta about dd-trace-dotnet

[vadimi]

Based on https://docs.microsoft.com/en-us/windows/desktop/sysinfo/acquiring-high-resolution-time-stamps#resolution-precision-accuracy-and-stability calculating duration like that works fine in Windows and Linux:

var start = Stopwatch.GetTimestamp();
await Task.Delay(100);
var end = Stopwatch.GetTimestamp() - start;
double elapsedMs = end * (1000.0 / Stopwatch.Frequency);

[lucaspimentel]

Thanks for reporting this. We'll look into it right away.

[lucaspimentel]

Interestingly, in DateTimeOffset.AddTicks() a tick seems to always be 100 nanoseconds, but the length of ticks in Stopwatch.ElapsedTicks can vary by platform (see also Stopwatch.Frequency).

[lucaspimentel]

@vadimi: The issue should now be fixed in 0.8.2, so I'm closing this issue. Thanks again for reporting it.