JetBrains Rider's unit test runner does not allow running two or more tests with the same ID. This rarely happens in practice, but if you do have tests with the same ID, they will appear as a single node in the Unit Tests window, and only one of them will run.
Note that test frameworks identify tests in different ways. For example, MSTest uses test-methods FQNs but NUnit uses properties of test attributes as test IDs.
JetBrains Rider allows you to check your code for all kinds of memory issues right from your unit tests using JetBrains dotMemory Unit.
As soon as you reference the dotMemory Unit Testing Framework, JetBrains Rider will add Run under dotMemory UnitCtrl0U,0M to other unit testing actions, so that you will be able to make your unit tests pass or fail depending on memory traffic, presence of specific objects in memory, and other factors. For more information, refer to Unit Testing and Memory Profiling: Can They Be Combined?