Given an application that involves, say, Companies, I might have a Company class. I will have a data access layer that populates a List
That sounds like a reasonable approach to me.
Later on, if the customer comes to you asking for your SearchResult
to display something unrelated to the Company
model - something crazy like the number of nearby ice cream shops you'll have a much easier time appending this to your CompanySearchResult
than your domain object.