C# Code coverage of a DLL called by a powershell script

This is about dbatools. A powershell module written in PowerShell that uses a C# DLL for some of its code.

The C# code is tested by MSTest (I wrote 99% of these tests), the Powershell code is tested by Pester. Pester generates PowerShell code coverage reports, but not C# Code coverage reports. Is there a way to make it do that?

Ultimately, while there are C# unit tests, some things are better tested in Pester, or need to be tested in Pester.

Finally, understanding what C# code paths aren't exercised by pester is a good tool for figuring out unused C# code.