Thanks for the response.

Your reply made the penny drop and rather than view the clustered index as an index and therefore index seeks/scans if I think of it as an ordered table it all makes sense!

I'm guessing that to avoid so many bookmark lookups I should add the missing field(s) causing the bookmark lookup to either the nonclustered or clustered index or add the field to the nonclustered index as an included column.