Does anyone have any concrete examples of a simple Unit of Work pattern in C# or Visual Basic that would handle the following scenario?

I'm writing a WinForms application in which a customer can have multiple addresses associated with it. The user can add, edit and delete addresses belonging to the customer before the customer is saved back to the database. Therefore, at the time of saving, all the original addresses need to be deleted from the database and the new addresses added in a single transaction.