Its just the unloved middle child of programming languages. C++ standard tries to be for high level, but still can't escape the low level baggage, see the whole Boost library that tries to add in what they thought was missing from the standards but there's still low level details spilled everywhere, see the docs for regex matching:
https://www.boost.org/doc/libs/release/libs/regex/doc/html/boost_regex/ref/match_results.html
If you wanted low level, C does everything already. If you wanted high level, you could just do python, Java or C#, they too have all the C++ standard library routines bundled. You could even write high level bindings in C if you need the occasional low level routines.
There's also the bad aftertaste of C++ programmers ruining all the fun out of it by writing line noise like code in the early days of object oriented programming before practices properly formalize, at least with perl, its usually out of sight, out of mind. You can take a look at the nasty stuff the earlier C++98/C++03 standards had to go through at
https://yosefk.com/c++fqa/, yes you can explicitly call the destructors on a local variables explicitly before it goes out of scope, it only makes sense on fixed memory embedded systems, but it is there and requires all implementations to support it.
Edit: The C++ Standards governs API (Application Programming Interface), it does not govern ABI (Application Binary Interface) and you must recompile everything if you change standards, this applies to all underlying dependent libraries underneath too. Sometimes you end up with the same libraries installed multiple times for different C++ standards. It just can't escape all the low level details properly unless you took explicit action to isolate all interfaces. Inb4 you end up with an inner-platform effect.
