Handling manufacturer mergers Is there a standard pattern for linking products to manufacturers, when we want to capture the fact that manufacturers are interacting with each other over time (mergers, takeovers, etc)?

In our industry, company A makes product 1, and many people refer to that product with a token like "A-1" when talking about it or trying to look up detailed performance and physical characteristics of that product in our database.

If company B purchases A, we still want to be able to allow people to use a token like "A-1" to look up the performance data of that product, even though the owning company is now B. A new user meanwhile can look at the records and understand that company A made the product and is the former owner, while company B is now the "real" owner.

Is it viable to model this with two manufacturer foreign keys, and a version column that would increment when the manufacturer relationship changes? The version column would be used to allow the older "A owns 1" row to remain in the table for existing records that linked to it at the time A owned 1 before being bought out by B.
This is how I might approach this design... by adding an ID for the original manufacturer at the Product level, then storing the details in a history table.

The history table would allow for Manufacturer IDs (or other details) to change over time to be stored without a need for version numbers.  

Product table

Product_ID
Product_Name
Orig_Mfgr_ID

Product History table

Product_ID
ProductHistory_ID
Orig_Mfgr_ID
Mfgr_StartDate
Mfgr_EndDate
CreateDate

I would then create a view or function to pull the most recent/current manufacturer based on the purchase date of the product, rather than storing this information in the Product table itself.