What were the suspicious error messages you spoke of previously?

You've got a few, equally unpleasant choices:

1) restore back to a backup from before the corruption occured

2) extract out the data into a new database, or just live with DBCC CHECKDB always raising this error

3) manually hack the underlying system tables to remove the broken data.

I recommend #1 or #2. #3 is possible (I demo it at conferences) but I don't know which table you'd need to change to fix this particular problem.