The picture is in fact a bit more than "just speed".

You have too also look at the code and the workload that you are running.

Code:

the more complex computation and logic, the more you will benefit from natively compiled stored procedures. - On the opposite: if your procedure consists of nothing than a pure “INSERT INTO xyz” and that’s it, you will probably not see a performance gain and it can even be slower (!)

The picture changes again, if you have a lot of such inserts coming in within a batch.

Workload:

The more you have Updates the less you will benefit from the In-Memory Optimized Tables because of the version chains.

Also for a pure read-workload in OLAP style consisting of thousands of rows returned, you’d better go with Clustered ColumnStore Indexes.

That’s not everything but should get you an idea.