I can see previous issue being fixed in an unofficial version - did it ever make it to stable release? The issue still exist with running test in parallel with vstest code coverage (XPlat code coverage)