While this answer sounds like a critique of Anton's answer, it's really a critique of your question.
The citation in Anton's answer says "yes, you can profile unit tests". In the same way that a debugger can debug unit tests. It does NOT say "and you can automatically dump it to disk and compare it to a previous run using this commandline option". All it says is "there is no reason why the thing you're profiling cannot be your DLL sitting inside a test runner - we don't just profile EXEs you wrote you know"
Even if there were settings to run from commandline and capture, what would you do with it? Are there tools that come with it that let you say "and complain if this falls outside of this tolerance" that can then act like a failing test and come out in the build report?
You dont use a profiler for stuff like this, you do normal performance tests with timings as a normal unit test would.