we’ve seen this problem with xunit and needed to use the -noshadow option to avoid creating shadow copies of assemblies - as the shadow copies were getting analyzed and lead to duplicate coverage information
maybe you can investigate that on your side