Use this page to configure step filters in C++.
Why do you need step filters? Well, the illustration below explains pretty much everything:
Some functions never need to be stepped into because they are either very simple or very well tested. But the problem is that the debugger cannot tell which functions are worth debugging and which are not, and therefore Step Into will not miss any function on its way.
With ReSharper, you can maintain step filters — a list of function masks that tells the debugger what should be skipped on stepping. By default, this list includes a lot of library functions and it can be extended with your own function masks.
While debugging, you can quickly add a function to the filters: press Alt+Enter on that function and it will be added to the filters:
By default, this action saves the filter using the smart save logic, but you can also use the action's submenu to choose the settings layer where the filter should be saved.