Access all the way through 2010 supported source control, and this included support for the group creation server. The fact that you put all the files in one ZIP file, one folder on your hard drive, or in one container called accDB is the MOOT point. While EVERY individual object can be considered as a SEPARATE object, then why bothers you if you use a zip file or accDB file? This is a "logical" view compared to the problem of physical viewing.
A simple question: EACH OBJECT IN ACCESS MAY BE EXPORTED AS A TEXT OBJECT. Thus, Access supports integration with source code, using this ability with the standard Microsoft SCC interface since Access 97 access (it's over 17 years!).
When you use SCC, such as Visual Source safe or Team Foundation, then the BUILT IN user interface in Access supports displaying the state of objects. You have permission right down to the form, report, sql query, and code module level. Thus, several developers can work simultaneously with the application. They only need to check the forms, reports, etc., on which they work. Thus, each developer has his own local assembly.
If you are using Visual Source Safe, you will see this in the stream:
If you are using the team foundation server, you will see the following:
And for the marked objects you will see the following:
And when you open or even right-click on an object, you see the following additional options:
Of course, given that "few" use this feature or even know what it is (and SO posts confirm this lack of knowledge), it is not surprising that this feature was disabled in Access 2013 after all these years! However, some third-party add-ons require restore this ability. Thus, the possibility of exporting objects in 2013 as separate STILL text files remains in place.