Organize headers with highest import point/ as specific as possible?

When I organize included headers with CLion, it seems CLion picks headers that are lower in the header tree and include everything that is required, but also necessarily bring in declarations that are not required. This approach leads to a nice, compact and readable header list.

I dislike this style of import organisation, for three reasons:

1. It makes it harder to manually trace to your required declaration when you do not have IDE support.
2. It places additional onus on tools for dependency analysis.
3. It increases the risk that you will encounter preprocessor programming that you need to understand to analyze what is actually going on.

So please, CLion, can you organize my header imports as much as possible in such a way that I get the most specific headers, even if the list is long?