A Google Webmaster Central blog post by Sven of the Search Quality Team addresses underlying concerns regarding how Google handles scraped content. In the two scenarios discussed, one (duplicate content within your domain) can be controlled. The other cannot. However, he recommends that you offer a link back for syndicated content:

If scraped content ranks higher than the original content, it is probably a technical issue on your end (a “rare case,” says Sven). You should check that the content is not blocked out by robots.txt, see the sitemap file for any changes, or check if the site is in line with the Google Webmaster Guidelines.

The article concludes with some hopefully reassuring text:

WebmasterWorld members are not sure if the article is entirely accurate. One issue of contention is the statement that scraped content ranking higher than original content is a “rare case” (and that it’s really a technical issue that you’d be responsible for). Personally, I am in agreement with the forum members here as I’ve seen (and read about) the same thing happen(ing) many times.

Tedster makes an interesting observation: Google might get it right 99% of the time, but that 1% that they don’t get right will still bug you.

Another forum member says that sometimes scraped content is masked and it’s hard for Google to figure out what is the originating site:

Overall, webmasters agree that it’s not that easy to prevent content scrapers. Content scrapers are getting smarter and will try to avoid being detected by the big G.

Forum discussion continues at WebmasterWorld.