Pester code coverage for the longest time was based on break points and break points in PowerShell until 7.4, which will be released now are super slow. So I use the core of the new module profiler that I wrote to actually implement new version of code coverage inside of Pester. And so running tests on their profiler is definitely a great way to find slow code in your module because you exercise a lot of parts of your code. It gives a little bit more visibility into what the heck's going on.