Lectora and source/revision control software

We use version control software (Subversion) in our office to track changes and keep histories of our projects. This works great for our programming projects, but we're running into some issues using it with Lectora.

The project .awt file is just a text (xml) file, so one would assume that it would work well in a scenario like ours. However, every time we save, the awt file often changes in so many places that it usually causes conflicts when different developers go to check in their project. This makes it impractical to have two people working on the same project at the same time.

I was just wondering if anyone else uses source control software with Lectora projects, or how others deal with having development teams where multiple people must work on the same Lectora project. One alternative I've been considering is having different team members work in different project files, then have someone pull the different pieces together into a single project when ready. The first issue I can see with this is if some of the object rely on top-level actions or variables, those would have to be copied across the different projects and kept in sync. I'm sure there are other logistical issues as well.