Here's a strange one, for any custom developers out there.

I have a custom site definition, and in all of the page template files,
I reference a custom site navigation control that accesses a list -
called Navigation - that is used throughout my site.

For every SharePoint control that appears afterwards that reference that
page's list, the reference is changed to the list - i.e., Announcements
- that I am trying to access in my control.

So for example, if I go to the All Items page in the Announcements list,
the various SharePoint controls are shown on the page in the following
order, with the following behavior:
1) HTML page title control (in between the <title> tags) - Displays
Announcements, as expected
2) My navigation control - Displays the navigation, as expected
3) Page Display Title, underneath the site title - Displays Navigation
4) Views control - Lists the various views for the Navigation list
5) Alert Me - Links to creating an alert for the Navigation list
6) Modify My Settings and Columns - Links to modifying the settings for
the Navigation list.

So what gives? When I refer in my control's code to the Navigation list,
shouldn't that reference fall out of scope after the control is through
rendering?

Anyone ever encountered a similar error?