Dethroning C++

I've designed a checklist that would instantly decide if language will be a C++ successor or not. Every line is requirement for a "language that will dethrone C++", 9/10 wouldn't cut it.
1.No dependencies on GC/refcounting.
2.Object abstraction system(as powerful as in C++).
3.Same or better execution speed(compared to similar C++ code).
4.Type-inference,type-inferred lambda expression.
5.Strict type system with escapes(fast casts, conversion).
6.Clear and terse imperative syntax.
7.Large standard library with functional/OOP/procedural programming support. Must include threading and graphics.
8.Support for low-level code(such as inline assembler and OS/hardware interfaces).
9.Text-generator(aka #define a(b)) and code-generator(template/mixin/lispmacro) macros.
10.Operator/function overloading without restrictions.

>>2
The "multi-paradigm way, there many ways to do it" always wins over pure dogmatic "one way - my way" systems. The list is actually the minimum of features the C++-dethroning language must have to have a chance to win the hearts of developers.
They must see advantages vs C++:
simpler and faster code.
better syntax. Larger standard library.
better architecture, object systems.
better error checking, compiler support.
If critical feature X is working better in C++ than in "new language" they wouldn't consider switching since switching cost is not justified. Switching cost is always high and needs to be counterbalanced with advantages of switching.