In Entity Framework code-first, why are primary ke

Question

I'm learning more about indexes in general, and clustered indexes in particular.

In this article by Markus Winand, he makes an excellent case for not using the primary key of a table as the clustering key.

He stresses index-only scans over using clustered indexes, and shows how you can use non-clustered indexes to get really fast results.

Can someone explain why Entity Framework code-first does not provide the means to store a table as a non-clustered-index?

What are the benefits of having every table clustered?