While checking missing indexes statistics I found there recommendations for high impact new indexes that have primary key (that are also clustered key in their tables) columns among "included" columns.
E.g., image below, szTransactionId field is a primary key and a clustered index column in the table, and is in the "included" columns for several missing indexes:
Similar, itemId + version columns make a clustered key on another table, and, again, are in the "included" list of a missing index:
I just read in Navarez's "Inside SQL query optimizer..." (in addition to what I already knew on the subject): "When a non-clustered index is created on a table with a clustered index, each non-clustered index row also includes the table clustered key". So why do the missing indexes still recommend to include clustered keys?