The LIKE operator can be used with In-Memory tables with ordinary (i.e Interop) SQL queries.
It can't be used in the natively-compiled procedures, but then almost nothing can. Microsoft specifies what *can* be used, rather than what can't be used.
What I would like to see in SQL Server 2016 In-Memory OLTP is:
• the ability to create indexes on nullable columns;
• Constraints — Foreign key, check und unique;
• Outer joins in natively-compiled procedures;
• Alter Table — at the moment one has to drop a table and recreate it if you want to make a change, add a column, rename it etc.;
• cross-database queries — although linked servers work;
• Sub-queries in natively-compiled subqueries;
This technology is only half-way here. It reminds me of using MySQL back in the 1990s — promising, not yet ready for migrations of currently used systems and maybe suitable for a new application so that the DB and application can be designed around its limitations.