Microsoft Sync Framework 2.1 + Change Tracking in Sql-Server 2008

When I provision a scope for synchronization in an SQL 2008 database like this:

SqlSyncScopeProvisioning sqlServerProv = new SqlSyncScopeProvisioning(sqlServerConn, myScope);
if (!sqlServerProv.ScopeExists(scopeName))
{
   sqlServerProv.Apply(); // Apply the scope provisioning.
}

i see a bunch of change tracking tables, stored procedures and triggers created. Why is this not using the "Change Tracking" feature of SQL 2008, which is much cleaner and everything gets track开发者_运维知识库ed behind the scenes? I thought that the "Change Tracking" feature of SQL 2008 was designed precisely to simplify these scenarios.

Now turning the question around: Is there a way to do a 2-way synchronization between two SQL Server 2008 databases just using Change Tracking in both of them instead of provisioning the triggers/auxiliary tables ?

---

See Syncing SQL Server 2008 Databases over HTTP using WCF & Sync Framework